@bors try @rust-timer queue

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

⌛ Trying commit ecb0a11 with merge 1423a52492255f39b3f99dd40f9e7a61bca4c1db...

☀️ Try build successful - checks-actions
Build commit: 1423a52492255f39b3f99dd40f9e7a61bca4c1db (1423a52492255f39b3f99dd40f9e7a61bca4c1db)

Queued 1423a52492255f39b3f99dd40f9e7a61bca4c1db with parent f262ca1, future comparison URL.

Finished benchmarking commit (1423a52492255f39b3f99dd40f9e7a61bca4c1db): comparison url.

Summary:

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: changes not relevant. 1 results were found to be statistically significant but the changes were too small to be relevant.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression